Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
contribute:bugs:start [2018/11/17 22:59] – [Bug Reporting] alexxcons | contribute:bugs:start [2024/05/31 23:31] (current) – removed outdated information alexxcons | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Bug Reporting | + | ~~NOTOC~~ |
+ | {{ : | ||
+ | ====== Bug Reporting | ||
- | One of the most useful tasks that we rely on the community for is testing and reporting of bugs. Since Xfce runs on various | + | One of the most useful tasks that we rely on the community for is the testing and reporting of bugs. Since Xfce runs on various |
- | ===== Fixing Bugs ===== | + | ---- |
- | Once a bug has been found, the cause of the bug needs to be tracked down, and then (obviously) fixed. If you want to get involved in the actual development process of Xfce a great way to start is by solving bugs and attaching a patch file to the reported bug. ( "git format-patch" | + | ===== Crashes ===== |
- | Not familiar | + | We always try to make the Xfce Desktop Environment as stable as possible; but, there is always a possibility that a crash, exception, or a segmentation fault(segfault) may occur. The problem |
- | After you managed | + | There are a couple of things |
- | ===== Feature Requests ===== | + | |
- | Although the philosophy of Xfce is to find the correct balance between features and lightweight, | + | ---- |
- | This right approach for larger changes is to discuss them on the mailing list first. You might think your idea is brilliant, but there is a high possibility other users. | + | ==== Search First ==== |
+ | Search the open issues of the project | ||
- | Afterwards a bug can be opened in the bug tracker and make sure the // | + | ---- |
- | Obviously its also nice if you can write a patch that implements the feature, but its not a necessity. | + | ==== Report ==== |
- | ===== Crashes ===== | ||
- | We always | + | When writing your bug report, |
- | + | ||
- | Nonetheless there are a couple of things you can do to help resolving them: | + | |
- | + | ||
- | ==== Search First ==== | + | |
- | Search the [[https://bugzilla.xfce.org|bug tracker]] and look if the issue is already known. Also look through the resolved bugs because the issue might be fixed already, but has not been released or applied downstream. Peeking the [[http://git.xfce.org/xfce|GIT repository]] might help for the latter. | + | |
- | + | ||
- | ==== Report ==== | + | |
If you have not found anything or missed it, report it in the bug tracker. Reports that only say ' | If you have not found anything or missed it, report it in the bug tracker. Reports that only say ' | ||
Line 36: | Line 30: | ||
If the developer cannot reproduce it, he might ask for a // | If the developer cannot reproduce it, he might ask for a // | ||
+ | |||
+ | [[|Back To Top]] | ||
+ | ---- | ||
==== Backtraces ==== | ==== Backtraces ==== | ||
Line 54: | Line 51: | ||
* [[http:// | * [[http:// | ||
* [[https:// | * [[https:// | ||
+ | |||
+ | [[|Back To Top]] | ||
+ | ---- | ||
+ | |||
+ | ===== Fixing Bugs ===== | ||
+ | |||
+ | Once a bug has been found, the cause of the bug needs to be tracked down, and then (obviously) fixed. If you want to get involved in the actual development process of Xfce a great way to start is by solving bugs and attaching a patch file to the reported bug. ( "git format-patch" | ||
+ | |||
+ | Not familiar with git? [[contribute/ | ||
+ | |||
+ | To get started, best read our [[contribute/ | ||
+ | |||
+ | |||
+ | [[|Back To Top]] | ||
+ | ---- | ||
+ | [[ : |